View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000773 | T99X171.00 SKB Eagle | SW Issue | public | 2019-08-30 17:00 | 2020-09-28 14:07 |
| Reporter | Assigned To | Due Date | |||
| Priority | normal | Severity | s2-severe | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0000773: [Eagle][common] BT Paring issue with New patch from Cypress | ||||
| Description | I tested BT pairing with Movon RCU and Remote Solution RCU alternately We use SW v17.510.05 for AOSP. I think it is added some modification from Cypress. BMM (Movon) sucess( 30) code 33( 8) code 11 (9) BRM (Remote Solution) sucess( 30) code 33( 6) code 11 (10) | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) SY Yoon , (SW) Jacky Chiang |
|---|
|
|
Hi Jason, I attached the compare results of different bt fw about the pairing issue. The test is in a clean environment that do not have other BT and WiFi signal to avoid any interference that will impact the result. You can see the result of new bt fw is behavior the same compared to old bt fw we used in r43 that passed the previous BMT. |
|
|
hi river i have tested with V06 for AOSP , V50 forATV. - For fixing NUGU recognition sometimes is wrong when earphone is connected to RCU and easy to have Code33 error when different RCU epairs repeatedly (Replace BT fw with version CYW20703A2_001.002.011.0296.0315.) This patch is applied in V50 and V05. My test result is shown as below. RCU brand's name is Moven. AOSP v06 - sucess(30), code 11(3), code33(11) ATV V50 - Sucess(30), code 11(2), code 33(10) it is diffrent from your result (an enclosed file). Could you check it in your side ? I'm not sure a fail ratio is high more than before. Thanks. |
|
|
Hi Jason, The bluetooth firmware you used is the same fw as the test result in excel. It should not make any difference between AOSP and ATV. For your test result, could you help to confirm the following things: 1.Which RCU software version do you use for testing? We use Remote Solution/Moven v1.4. 2.Are there many bt devices in your test environment? If many bt devices in your test environment, the test result will vary and it will be easy to have interference. 3.Is it a BMT test item to use different RCU to do crossing pair? What is the criteria for this test item? Because we think that this test case is rare for field users. 4.When RCU fails to pair but there is no Code11/Code33 message in UI, how do you count this case in your test result or just ignore it? |
|
|
Hi River I reply your mail. The bluetooth firmware you used is the same fw as the test result in excel. -> Excel : v48 version -Replace BT fw with version CYW20703A2_001.002.011.0306.0313. My FW : V50 Version - BT fw with version CYW20703A2_001.002.011.0296.0315.) a backend Digit of BT FW is a little difference. You mean is it same FW? 1.Which RCU software version do you use for testing? We use Remote Solution/Moven v1.4. --> Yes. only Moven 01.40 2.Are there many bt devices in your test environment? If many bt devices in your test environment, the test result will vary and it will be easy to have interference. --> when I try to have tested, there is no person to try to pairing around me. 3.Is it a BMT test item to use different RCU to do crossing pair? What is the criteria for this test item? Because we think that this test case is rare for field users. --> My test is used with only Moven RCU. Didn't try to do crossing pair. 4.When RCU fails to pair but there is no Code11/Code33 message in UI, how do you count this case in your test result or just ignore it? --> My result only was counted via shown on UI. Thanks. |
|
|
Hi Jason, We got the new bluetooth firmware from cypress and do some modifications to improve the RCU pairing. As I tested on this firmware with Moven RCU based on this modification, the result for only pairing one RCU repeatedly is following: ATV V50 with new bt firmware and modifications - Sucess(30), code 11(1), code 33(5) . The Code33 is caused by the RCU is abnormal, after I re-plug the battery, it becomes normal again. But I think the test result will vary for RCU pairing, because sometimes RCU has problem to be scanned or too many bluetooth devices in test environment (It is not necessary to do pairing nearby) or WiFi 2.4G traffic interference. I already commit the bluetooth firmware and modification. It will be included after R51. |
|
|
Hi river I tested with v53. my result is shown as below. it seem increasing a performance. Success(30) / code11 (1) / code33 (7) this status is changed as resolve. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-08-30 17:00 |
|
New Issue | |
| 2019-08-30 17:01 |
|
Description Updated | |
| 2019-09-05 14:21 | (SW) Jacky Chiang | Assigned To | => (SW) River Wong |
| 2019-09-05 14:21 | (SW) Jacky Chiang | Status | new => assigned |
| 2019-09-05 17:39 |
|
File Added: Compare_result_of_different_bt_fw_for_pariing_Moven_RemoteSolution_RCU.xlsx | |
| 2019-09-05 17:39 |
|
Note Added: 0002956 | |
| 2019-09-09 20:34 | (SW) Jacky Chiang | Issue Monitored: (SW) Jacky Chiang | |
| 2019-09-10 12:26 |
|
Issue Monitored: (ALTech) SY Yoon | |
| 2019-09-20 11:46 |
|
Note Added: 0003040 | |
| 2019-09-24 19:12 |
|
Note Added: 0003050 | |
| 2019-09-25 09:49 |
|
Note Added: 0003052 | |
| 2019-09-27 18:46 |
|
Note Added: 0003069 | |
| 2019-10-07 17:01 |
|
Status | assigned => resolved |
| 2019-10-07 17:01 |
|
Resolution | open => fixed |
| 2019-10-07 17:01 |
|
Note Added: 0003082 | |
| 2020-09-28 14:07 |
|
Status | resolved => closed |
